-- *******************************************************************
-- CISCO-LWAPP-CDP-MIB.my
-- Mar 2007 , Ambika Prasad Mohanty
-- Copyright (c) 2007 by Cisco Systems Inc.
-- All rights reserved.
-- ******************************************************************CISCO-LWAPP-CDP-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,Unsigned32,Counter32FROM SNMPv2-SMI
MODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF
DisplayString,TruthValueFROM SNMPv2-TC
SnmpAdminStringFROM SNMP-FRAMEWORK-MIB
InetAddress,
InetAddressTypeFROM INET-ADDRESS-MIB
InterfaceIndexOrZeroFROM IF-MIB
cLApSysMacAddress
FROM CISCO-LWAPP-AP-MIB
CLCdpAdvtVersionType
FROM CISCO-LWAPP-TC-MIB
ciscoMgmt
FROM CISCO-SMI;-- ********************************************************************
-- * MODULE IDENTITY
-- ********************************************************************ciscoLwappCdpMIB MODULE-IDENTITYLAST-UPDATED"200703280000Z"ORGANIZATION"Cisco Systems Inc."CONTACT-INFO"Cisco Systems,
Customer Service
Postal: 170 West Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
Email: cs-wnbu-snmcp@cisco.com"DESCRIPTION
"This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight Access Point Protocol
tunnel from Light-weight LWAPP Access Points.
This MIB provides configuration and status information
about CDP neighbors of LWAPP APs. The MIB provides
configuration of CDP feature on the LWAPP Access Points.
The MIB can also be used to retrive the status of the
CDP cache information on the various LWAPP LWAPP Access
Points.
The CDP MIB is also supported by Controller and provides
configuration and status information about CDP neighbours
of the controller.
The relationship between CC and the LWAPP APs
can be depicted as follows:
+......+ +......+ +......+ +......+
+ + + + + + + +
+ CC + + CC + + CC + + CC +
+ + + + + + + +
+......+ +......+ +......+ +......+
.. . . .
.. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ AP + + AP + + AP + + AP + + AP +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
+......+ +......+ +......+ +......+ +......+
+ + + + + + + + + +
+ MN + + MN + + MN + + MN + + MN +
+ + + + + + + + + +
+......+ +......+ +......+ +......+ +......+
The LWAPP tunnel exists between the controller and
the APs. The MNs communicate with the APs through
the protocol defined by the 802.11 standard.
LWAPP APs, upon bootup, discover and join one of the
controllers and the controller pushes the configuration,
that includes the WLAN parameters, to the LWAPP APs.
The APs then encapsulate all the 802.11 frames from
wireless clients inside LWAPP frames and forward
the LWAPP frames to the controller.
GLOSSARY
Access Point ( AP )
An entity that contains an 802.11 medium access
control ( MAC ) and physical layer ( PHY ) interface
and provides access to the distribution services via
the wireless medium for associated clients.
LWAPP APs encapsulate all the 802.11 frames in
LWAPP frames and sends it to the controller to which
it is logically connected.
Basic Service Set Identifier (BSSID)
The identifier for the service set comprising of
all the 802.11 stations under the control of
one coordinating Access Point. This identifier
happens to be the MAC address of the dot11 radio
interface of the Access Point. The wireless
clients that associate with the Access Point
get the wired uplink through this particular
dot11 interface.
Central Controller ( CC )
The central entity that terminates the LWAPP protocol
tunnel from the LWAPP APs. Throughout this MIB,
this entity also referred to as 'controller'.
Light Weight Access Point Protocol ( LWAPP )
This is a generic protocol that defines the
communication between the Access Points and the
Central Controller.
Cisco Discovery Protocol ( CDP )
Protocol for discovery of neighboring devices.
REFERENCE
[1] Part 11 Wireless LAN Medium Access Control ( MAC )
and Physical Layer ( PHY ) Specifications.
[2] Draft-obara-capwap-lwapp-00.txt, IETF Light
Weight Access Point Protocol."REVISION"200703280000Z"DESCRIPTION"This is the initial version of this module."::={ ciscoMgmt 623}
ciscoLwappCdpMIBNotifs OBJECTIDENTIFIER::={ ciscoLwappCdpMIB 0}ciscoLwappCdpMIBObjects OBJECTIDENTIFIER::={ ciscoLwappCdpMIB 1}ciscoLwappCdpMIBConform OBJECTIDENTIFIER::={ ciscoLwappCdpMIB 2}clcCdpTraffic OBJECTIDENTIFIER::={ ciscoLwappCdpMIBObjects 1}clcCdpGlobalConfig OBJECTIDENTIFIER::={ ciscoLwappCdpMIBObjects 2}
clcCdpApCacheStatus OBJECTIDENTIFIER::={ ciscoLwappCdpMIBObjects 3}clcCdpApCacheConfig OBJECTIDENTIFIER::={ ciscoLwappCdpMIBObjects 4}-- *******************************************************************
-- The CDP Traffic Metrics
-- *******************************************************************clcCdpInPackets OBJECT-TYPESYNTAXCounter32UNITS"packets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Count of total CDP packets received by the Controller."::={ clcCdpTraffic 1}
clcCdpOutPackets OBJECT-TYPESYNTAXCounter32UNITS"packets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Count of total CDP packets sent by the Controller."::={ clcCdpTraffic 2}clcCdpChecksumErrorPackets OBJECT-TYPESYNTAXCounter32UNITS"packets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Total number of CDP packets that experienced
checksum error."::={ clcCdpTraffic 3}
clcCdpNoMemoryPackets OBJECT-TYPESYNTAXCounter32UNITS"packets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Total number of CDP packets that were dropped
because of no memory availability."::={ clcCdpTraffic 4}clcCdpInvalidPackets OBJECT-TYPESYNTAXCounter32UNITS"packets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Total number of CDP packets that were invalid."::={ clcCdpTraffic 5}-- ********************************************************************
-- * Global CDP Configuration
-- ********************************************************************clcCdpAdvtVersion OBJECT-TYPESYNTAX CLCdpAdvtVersionType
MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"Cisco Discovery Protocol advertisement version."DEFVAL{ cdpv1 }::={ clcCdpGlobalConfig 1}clcCdpMessageInterval OBJECT-TYPESYNTAXUnsigned32(5..900)
UNITS"seconds"MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The interval (in seconds) at which CDP messages
are to be generated."DEFVAL{60}::={ clcCdpGlobalConfig 2}clcCdpGlobalEnable OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This is a template variable to enable / disable CDP
on all APs.
When 'true' is set, then internally CDP is enabled
on all APs associated with the Controller.
When 'false' is set, then internally CDP is disabled
on all APs associated with the Controller.
However, setting this attribute has no effect when CDP
is disabled globally, that is when the cdpGlobalRun from
the CISCO-CDP-MIB is set to 'false'on the Controller."DEFVAL{ false }::={ clcCdpGlobalConfig 3}-- *******************************************************************
-- The CDP configurations at AP level
-- *******************************************************************clcCdpApTable OBJECT-TYPESYNTAXSEQUENCEOF ClcCdpApEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The (conceptual) table containing the status of Cisco
Discovery Protocol on LWAPP Access Points. An entry is added
to the table when an Aceess Point joins a controller. An entry
is deleted when the Access Point disassociates from the
controller. This table is used to configure CDP feature per Access
Point."::={ clcCdpApCacheConfig 1}clcCdpApEntry OBJECT-TYPESYNTAX ClcCdpApEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry (conceptual row) in the clcCdpApTable,
containing the status of CDP on an AP.
Consider a setup where two APs, 'AP1' and 'AP2'
have been connected to a CISCO-3750 switch.
Both the APs register with WLAN CONTROLLER 440x
which is on LAN/Internet/Intranet.
+.........................+
+ +
+ WLAN CONTROLLER 4400 +
+ 10.14.2.11 +
+.........................+
..
..
INTERNET .. LAN
..
+...............+
+ +
+ SWITCH-3750 +
+ 10.16.1.1 +
+...............+
..
. .
. .
. .
. .
. .
+......+ +......+
+ + + +
+ AP1 + + AP2 +
+ + + +
+......+ +......+
00:12:CF:DA:29:11 23:43:CE:9A:66:76
10.16.1.43 10.16.1.45
Given the above example, the clcCdpApEntry on
WLAN CONTROLLER 4400 looks like :
------------------------------------------------------------------
| MIB - ATTRIBUTES | ROW#1 | ROW#2 |
------------------------------------------------------------------
| cLApSysMacAddress | 00:12:CF:DA:29:11 | 23:43:CE:9A:66:76 |
------------------------------------------------------------------
| clcCdpApStatus | true | false |
------------------------------------------------------------------"INDEX{ cLApSysMacAddress }::={ clcCdpApTable 1}
ClcCdpApEntry ::=SEQUENCE{
clcCdpApCdpEnable TruthValue}clcCdpApCdpEnable OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"An indication of whether the Cisco Discovery Protocol
is currently running on this AP.
When set to 'true', that means CDP is enabled on
the AP denoted by MAC address cLApSysMacAddress.
When set to 'false', that means CDP is disabled on
the AP denoted by MAC address cLApSysMacAddress.
This variable has no effect when CDP is globally
disabled. That is when the cdpGlobalRun from the
CISCO-CDP-MIB is set to 'false'."DEFVAL{ false }::={ clcCdpApEntry 1}-- *******************************************************************
-- The CDP-AP Address Cache Table
-- *******************************************************************clcCdpApCacheTable OBJECT-TYPESYNTAXSEQUENCEOF ClcCdpApCacheEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the cached neighbor
information obtained via receiving CDP messages on APs.
Entries are added to this table when a CDP advertisement
is received from a neighboring device. Entries get deleted
when CDP is disabled on the interface or globally."::={ clcCdpApCacheStatus 1}clcCdpApCacheEntry OBJECT-TYPESYNTAX ClcCdpApCacheEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in the clcCdpApCacheTable,
containing the information received via CDP on one
interface from one device. Entries appear when
a CDP advertisement is received from a neighbor
device. Entries disappear when CDP is disabled
on the interface or globally.
Consider a setup where two APs, 'AP1' and 'AP2'
have been connected to a CISCO-3750 switch.
Both the APs register with WLAN CONTROLLER 4400
which is on LAN/Internet/Intranet.
+.........................+
+ +
+ WLAN CONTROLLER 4400 +
+ 10.14.2.11 +
+.........................+
..
..
INTERNET .. LAN
..
+...............+
+ +
+ SWITCH-3750 +
+ 10.16.1.1 +
+...............+
FE 0/13 .. FE 0/15
. .
. .
. .
. .
. .
+......+ +......+
+ + + +
+ AP1 + + AP2 +
+ + + +
+......+ +......+
00:12:CF:DA:29:11 23:43:CE:9A:66:76
10.16.1.43 10.16.1.45
Given the above example, the clcCdpApEntry on
WLAN CONTROLLER 4400 looks like :
----------------------------------------------------------------------
| MIB - ATTRIBUTES | ROW#1 | ROW#2 |
----------------------------------------------------------------------
| cLApSysMacAddress | 00:12:CF:DA:29:11 | 23:43:CE:9A:66:76|
----------------------------------------------------------------------
| clcCdpApCacheDeviceIndex | 16 | 16 |
----------------------------------------------------------------------
| clcCdpApCacheApName | AP1 | AP2 |
----------------------------------------------------------------------
| clcCdpApCacheApAddressType | ip(1) | ip(1) |
----------------------------------------------------------------------
| clcCdpApCacheApAddress | 10.16.1.43 | 10.16.1.45 |
----------------------------------------------------------------------
| clcCdpApCacheLocalInterface | Port - 1 | Port -2 |
----------------------------------------------------------------------
| clcCdpApCacheNeighName | SWITCH-3750 | SWITCH-3750 |
----------------------------------------------------------------------
| clcCdpApCacheNeighAddressType| ip(1) | ip(1) |
----------------------------------------------------------------------
| clcCdpApCacheNeighAddress | 10.16.1.1 | 10.16.1.1 |
----------------------------------------------------------------------
| clcCdpApCacheNeighInterface | FE 0/13 | FE 0/45 |
----------------------------------------------------------------------
| clcCdpApCacheNeighVersion | IOS Ver2.2. ... | IOS Ver 2.2. ... |
----------------------------------------------------------------------
| clcCdpApCacheAdvtVersion | cdpv1(1) | cdpv2(2) |
----------------------------------------------------------------------
| clcCdpApCachePlatform | WS-C3750-24P | WS-C3750-24P |
----------------------------------------------------------------------
| clcCdpApCacheCapabilities | RSI | RSI |
----------------------------------------------------------------------
| clcCdpApCacheHoldtimeLeft | 179 | 165 |
----------------------------------------------------------------------"INDEX{
cLApSysMacAddress,
clcCdpApCacheDeviceIndex
}::={ clcCdpApCacheTable 1}
ClcCdpApCacheEntry ::=SEQUENCE{
clcCdpApCacheDeviceIndex Unsigned32,
clcCdpApCacheApName SnmpAdminString,
clcCdpApCacheApAddressType InetAddressType,
clcCdpApCacheApAddress InetAddress,
clcCdpApCacheLocalInterface InterfaceIndexOrZero,
clcCdpApCacheNeighName DisplayString,
clcCdpApCacheNeighAddressType InetAddressType,
clcCdpApCacheNeighAddress InetAddress,
clcCdpApCacheNeighInterface DisplayString,
clcCdpApCacheNeighVersion DisplayString,
clcCdpApCacheAdvtVersion CLCdpAdvtVersionType,
clcCdpApCachePlatform DisplayString,
clcCdpApCacheCapabilities OCTETSTRING,
clcCdpApCacheHoldtimeLeft Unsigned32}clcCdpApCacheDeviceIndex OBJECT-TYPESYNTAXUnsigned32(0..2147483647)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A unique value for each device from which CDP messages
are being received."::={ clcCdpApCacheEntry 1}clcCdpApCacheApName OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Name assigned to this AP. If an AP is not configured its
factory default name will be ap:<last three byte of MAC
Address>.
eg. ap:af:12:be"::={ clcCdpApCacheEntry 2}clcCdpApCacheApAddressType OBJECT-TYPESYNTAXInetAddressTypeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"An indication of the type of address contained in the
corresponding instance of clcCdpApCacheAddress for the AP."::={ clcCdpApCacheEntry 3}clcCdpApCacheApAddress OBJECT-TYPESYNTAXInetAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This is the address of the AP.
For example, if the the corresponding instance of
clcCdpApCacheApAddressType had the value 'ip(1)', then this object
would be an IP-address."::={ clcCdpApCacheEntry 4}clcCdpApCacheLocalInterface OBJECT-TYPESYNTAXInterfaceIndexOrZeroMAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"This is the local port on which LWAPP encapsulated CDP
packets was received."::={ clcCdpApCacheEntry 5}clcCdpApCacheNeighName OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The Device-ID string as reported in the most recent CDP
message. The zero-length string indicates no Device-ID
field (TLV) was reported in the most recent CDP
message."::={ clcCdpApCacheEntry 6}clcCdpApCacheNeighAddressType OBJECT-TYPESYNTAXInetAddressTypeMAX-ACCESSread-only
STATUScurrentDESCRIPTION"An indication of the type of address contained in the
corresponding instance of clcCdpApCacheAddress of Neighbor."::={ clcCdpApCacheEntry 7}clcCdpApCacheNeighAddress OBJECT-TYPESYNTAXInetAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The (first) network-layer address of the device's
SNMP-agent as reported in the most recent CDP message.
For example, if the the corresponding instance of
clcCdpApCacheApAddressType had the value 'ip(1)', then this object
would be an IP-address."::={ clcCdpApCacheEntry 8}
clcCdpApCacheNeighInterface OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The Port-ID string as reported in the most recent CDP
message. This will typically be the value of the ifName
object (e.g., 'Ethernet0'). The zero-length string
indicates no Port-ID field (TLV) was reported in the
most recent CDP message."::={ clcCdpApCacheEntry 9}clcCdpApCacheNeighVersion OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The Version string refers to the software running on
neighboring device."::={ clcCdpApCacheEntry 10}clcCdpApCacheAdvtVersion OBJECT-TYPESYNTAX CLCdpAdvtVersionType
MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"Cisco Discovery Protocol advertisement version."DEFVAL{ cdpv1 }::={ clcCdpApCacheEntry 11}clcCdpApCachePlatform OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The Device's Hardware Platform as reported in the most
recent CDP message. The zero-length string indicates
that no Platform field (TLV) was reported in the most
recent CDP message."::={ clcCdpApCacheEntry 12}clcCdpApCacheCapabilities OBJECT-TYPESYNTAXOCTETSTRING(SIZE(0..32))MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The Device's Functional Capabilities as reported in the
most recent CDP message. For latest set of specific
values, see the latest version of the CDP specification.
The zero-length string indicates no Capabilities field
(TLV) was reported in the most recent CDP message."::={ clcCdpApCacheEntry 13}clcCdpApCacheHoldtimeLeft OBJECT-TYPESYNTAXUnsigned32(10..255)UNITS"seconds"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The time left, in seconds, before the CDP
neighbor entry gets aged-out."DEFVAL{180}::={ clcCdpApCacheEntry 14}-- *******************************************************************
-- * Compliance statements
-- *******************************************************************
ciscoLwappCdpMIBCompliances OBJECTIDENTIFIER::={ ciscoLwappCdpMIBConform 1}ciscoLwappCdpMIBGroups OBJECTIDENTIFIER::={ ciscoLwappCdpMIBConform 2}ciscoLwappCdpMIBCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for the SNMP entities that
implement the ciscoLwappCdpMIB module."MODULE-- this moduleMANDATORY-GROUPS{
clcCdpRev01ConfigGroup,
clcCdpRev01StatusGroup
}::={ ciscoLwappCdpMIBCompliances 1}
-- *******************************************************************
-- * Units of conformance
-- *******************************************************************clcCdpRev01ConfigGroup OBJECT-GROUPOBJECTS{
clcCdpApCdpEnable,
clcCdpAdvtVersion,
clcCdpMessageInterval,
clcCdpGlobalEnable
}STATUScurrentDESCRIPTION"This is a collection of objects which can
configured to control functional parameters
of Cisco Discovery Protocol feature in
WLAN controllers and LWAPP APs."::={ ciscoLwappCdpMIBGroups 1}clcCdpRev01StatusGroup OBJECT-GROUP
OBJECTS{
clcCdpApCacheApName,
clcCdpApCacheApAddressType,
clcCdpApCacheApAddress,
clcCdpApCacheLocalInterface,
clcCdpApCacheNeighName,
clcCdpApCacheNeighAddressType,
clcCdpApCacheNeighAddress,
clcCdpApCacheNeighInterface,
clcCdpApCacheNeighVersion,
clcCdpApCacheAdvtVersion,
clcCdpApCachePlatform,
clcCdpApCacheCapabilities,
clcCdpApCacheHoldtimeLeft,
clcCdpInPackets,
clcCdpOutPackets,
clcCdpChecksumErrorPackets,
clcCdpNoMemoryPackets,
clcCdpInvalidPackets
}STATUScurrentDESCRIPTION"This collection of objects represents the information
about the general status attributes of Cisco Discovery
Protocol in WLAN controllers and LWAPP APs."::={ ciscoLwappCdpMIBGroups 2}END